upgrade pinot lib to support new features introduced in Apache Pinot 0.9.3#17015
upgrade pinot lib to support new features introduced in Apache Pinot 0.9.3#17015highker merged 1 commit intoprestodb:masterfrom
Conversation
4445ee1 to
5c427ce
Compare
|
Hello, Do you know when you'll be able to end this PR? Thank you |
I'm still working on testing this feature, will update once I finished this. |
|
Great! Thank you for the update |
5c427ce to
72c8934
Compare
72c8934 to
1dce244
Compare
hopefully this week |
31c644e to
d61767d
Compare
e5f7ef4 to
e698b11
Compare
I've tested this locally with default mode and grpc mode, you can grab the code and test it as well. |
|
@dharakk please take a look once you got time. This is for pinot 0.9.3 upgrade, should be compatible with older pinot version, but better to test it with your own environment |
e698b11 to
6685ea4
Compare
6685ea4 to
9536e59
Compare
Thank you, I'll try in the day. I've already tested 2 days ago (so before last changes) and everything seemed to work except when I had a split that have 0 rows. Pinot doesn't return the data schema which leads to a Presto crash (i.e. when trying to call |
Sure, I assume you are using pinot server grpc endpoint right? The last block is metadata block, I've fixed that. Please give it a try. Let me know if there is any issue. |
Lgtm, issues I had are fixed |
Thanks for your validation! |
|
@highker please take a look once you got time! Thanks! |
|
this is to bring to your notice that I am not able to connect to any catalog when I run presto on my intellij on my M1 mac. This has been happening since I pulled this commit in my local machine. Errors like "bad file descriptor", "Could not create connection to database server. Attempted reconnect 3 times. Giving up" have been coming when I try to connect to any catalog from the cli on my laptop. @highker @xiangfu0 com.facebook.presto.spi.PrestoException: The connection attempt failed. |
Test plan - (Please fill in how you tested your changes)
Please make sure your submission complies with our Development, Formatting, and Commit Message guidelines. Don't forget to follow our attribution guidelines for any code copied from other projects.
Fill in the release notes towards the bottom of the PR description.
See Release Notes Guidelines for details.